home *** CD-ROM | disk | FTP | other *** search
- In article <2kbtut$ott@Mercury.mcs.com> karl@MCS.COM (Karl Denninger) writes:
-
- >In article <pjh.1720.2D696901@pjh.jvnc.net>,
-
- >>I've had the experience of having everything stop for periods of from seconds
- >>to 10s of seconds while using Trumpet Winsock, but I thought that was caused
- >>by the SLIP server.
- >>
-
- >NO! It is likely NOT your server! <VERY> brief (tenths to hundreths of
- >seconds) is acceptable; SLIP lines at 14.4 typically have ~230ms of
- >turnaround time delay. But anything significantly longer is either a
- >severely overloaded Ethernet on the other end or something broken.
-
- Well I borrowed a copy of a well-known commercial software and tried that for
- a day to see if there were differences and there weren't any.
-
- >I am now running another stack, which will remain nameless until I get done
- >with my evaluation. At which point you'll all hear about it. My first
- >impression -- THIS IS WONDERFUL STUFF -- CONSIDER NOTHING ELSE! It has
- >three huge wins - (1) it works, (2) it works, (3) it works.
-
- I'm looking forward to that.
-
- Pete
-
- ------------------------------------------------------------------
- Pete Holsberg The House On *This* Side Of U.S. 1
- 44 Lopatcong Drive pjh@mccc.edu
- Ewing, NJ 08638 pjh@pjh.jvnc.net
- FAX: 609-586-2318
- ------------------------------------------------------------------
- **** Trenton Computer Festival **** April 16-17, 1994 ****
- ------------------------------------------------------------------
- From news@bigblue.oit.unc.edu Fri Feb 25 15:00:47 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA01924; Fri, 25 Feb 1994 20:27:40 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA20759; Fri, 25 Feb 1994 20:01:22 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: Fri, 25 Feb 1994 20:00:47 EST
- From: patlee@panix.com (Patrick Lee)
- Message-Id: <patlee.263.005A30AA@panix.com>
- Organization: E-mail about Stuyvesant H.S. Alumni E-mail Directory
- Sender: ses
- References: <9402250352.AA11911@netmail2.microsoft.com>
- Subject: Re: Announcement: Bake-Off '94
-
- The following was posted to the info.ietf newsgroup ...
-
- In article <9402250352.AA11911@netmail2.microsoft.com> jallard@microsoft.com
- writes:
- >From: jallard@microsoft.com
- >Subject: Announcement: Bake-Off '94
- >Date: 25 Feb 94 01:48:14 GMT
-
-
- > ANNOUNCEMENT
-
- > The 1994 TCP/IP, Windows Sockets and PPP Bake-Off
-
- >Microsoft would like to follow the successful example provided last year
- >by FTP, TGV and InterCon Systems by hosting the 1994 TCP/IP bake-off.
- >Implementors of TCP/IP, Windows Sockets applications, and PPP products are
- >invited to come together in Redmond, WA to detect (and hopefully resolve)
- >any interoperability problems between products. The "bake-off" is held in
- >the spirit of multivendor cooperation with the goal of delivering
- >customers the finest possible range of interoperable internetworking
- >products.
-
- >The bake-off is specifically an engineering gathering. Developers and
- >architects should feel free to bring both present and beta implementations
- >of products to test reliability and interoperability in mixed internet
- >environments. Most implementors will choose to bring development and
- >debugging systems along so that fixes can be made and tested in real time.
- >The formal results of the interoperability testing will not be made public
- >- the intent of this event is solely to enhance the quality and
- >interoperability of the participants' products.
-
- >We plan to hold this event the week of April 18-22 - this is two weeks
- >following the Seattle IETF meeting, and two weeks before Spring Interop.
- >Once we receive feedback, we will draft and circulate a preliminary agenda
- >to the appropriate contact persons. We're hoping that we can expand the
- >scope of this annual event to include PPP and Windows Sockets testing as
- >well. Our current plan is to cover the following areas and protocols:
-
- >Base TCP/IP (ARP,ICMP,IP,UDP,TCP)
- >NetBIOS over TCP/IP (1001/1002)
- >DHCP (1533/1534/1541/1542)
- >Common IP Applications (FTP,Telnet,DNS, etc...)
- >TCP/IP printing (1179)
- >SLIP, PPP (both TCP/IP and IPX/SPX)
- >Windows Sockets API testing (WSAT)
- >Windows Sockets applications (interoperability matrix)
- >Windows Sockets 2.0 discussion
-
- >If you are interested please complete and return the following
- >questionaire to bakeoff@microsoft.com. Once we receive the initial
- >feedback from you, we will begin finalizing the schedule and logistics and
- >communicate all details to the contact persons.
-
- >Name of organization:
- >Contact person:
- >Contact e-mail:
- >Contact phone:
- >Will you be attending (Yes/No/Maybe):
- >Number of engineers attending:
- >What hardware will you be bringing:
- >What protocols are you interested in testing:
- >Special requirements:
- >Additional comments:
-
- >We're looking forward to hearing your comments and ideas on this year's
- >bake-off. Thanks for your interest and help in making this event
- >successful.
-
- >_______________________________________________________________
- >J. Allard jallard@microsoft.com
- >Program Manager of TCP/IP Technologies work: (206)882-8080
- >Microsoft Corporation home: (206)860-8862
- > "On the Internet, nobody knows you're running Windows NT"
-
- --
- Patrick Lee <patlee@panix.com>
- From news@bigblue.oit.unc.edu Sat Feb 26 01:30:31 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA05090; Fri, 25 Feb 1994 20:57:39 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA15333; Fri, 25 Feb 1994 20:30:30 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: Sat, 26 Feb 1994 01:30:31 GMT
- From: pjh@pjh.jvnc.net (Pete Holsberg)
- Message-Id: <pjh.1751.2D6EA636@pjh.jvnc.net>
- Organization: The House On This Side Of U.S. 1
- Sender: ses
- References: <2kgknq$1oo@Mercury.mcs.com>, <MCHEN.94Feb24123440@sol4.cse.psu.edu>, <2kk39a$79r@Mercury.mcs.com>
- Subject: Re: I'm ready to spend money - free and shareware WINSOCK not ok
-
- In article <2kk39a$79r@Mercury.mcs.com> karl@MCS.COM (Karl Denninger) writes:
-
- >> One further note:
- >>
- >> The Chameleon stuff I have here from the book does not, as far as I can
- >> determine, do dial-on-demand.
- >>
- >> Then again, TRUMPET WINSOCK internal SLIP claimed to support it but it
- >> didn't work right (launch a client and it dials, but the client immediately
- >> bitches about being unable to resolve a hostname and you have to start over
- >> anyway).
- >>
- >>What did you do, forget to fill in the domain and name server slots in the
- >>Setup option? Tsk tsk...
-
- >Reading? What's that?
-
- >Note that the client connects the <second> time. No, the problem is that
- >the call to resolve the name is returning before the line comes up, and
- >its coming back "no answer".
-
- >This is true for at least Trumpet and WinQVT. I learned quickly to tell it
- >to connect (opening it does the trick). On the other hand, you have to
- >click "CONNECT" on the Chameleon stuff. Big deal. If you get knocked off
- >you click the box again. No effect on your sessions as long as a keepalive
- >doesn't nail you. In fact, if you do lose the line it'll come up and ask
- >if you want to reconnect.
-
- I'm not sure what you mean by dial-on-demand. In both Trumpet Winsock and the
- Chameleon I borrowed, you have to launch a program and then do a little
- clicking to get it to dial and then log you in. After that, you invoke the
- E-mail or news reader or ftp or WinMosaic or whatever. ??
-
- Pete
-
- ------------------------------------------------------------------
- Pete Holsberg The House On *This* Side Of U.S. 1
- 44 Lopatcong Drive pjh@mccc.edu
- Ewing, NJ 08638 pjh@pjh.jvnc.net
- FAX: 609-586-2318
- ------------------------------------------------------------------
- **** Trenton Computer Festival **** April 16-17, 1994 ****
- ------------------------------------------------------------------
- From rcq@tri-flow.ftp.com Fri Feb 25 16:44:59 1994
- Received: from babyoil.ftp.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA10253; Fri, 25 Feb 1994 21:45:23 -0500
- Received: from tri-flow.ftp.com by babyoil.ftp.com with SMTP
- id AA22965; Fri, 25 Feb 94 21:45:47 -0500
- Received: from rcq.aeolus.ftp.com by tri-flow.ftp.com.ftp.com (5.0/SMI-SVR4)
- id AA04606; Fri, 25 Feb 94 21:44:59 EST
- Date: Fri, 25 Feb 94 21:44:59 EST
- Message-Id: <9402260244.AA04606@tri-flow.ftp.com.ftp.com>
- To: jellison@chaco.cs.unm.edu
- Subject: Re: IRC - What is it anyway? ;-)
- From: rcq@tri-flow.ftp.com (Bob Quinn)
- Reply-To: rcq@ftp.com
- Cc: Multiple recipients of list <winsock@sunsite.unc.edu>
- Sender: rcq@tri-flow.ftp.com
- Repository: slick-50.ftp.com
- Originating-Client: aeolus.ftp.com
- Content-Length: 1107
-
- > The subject says it all. I'm not familiar with IRC.
- >
- > Pointers to explanations or a brief descritpion would be real nice.
-
- >From the IRC FAQ I got at rtfm.mit.edu (the repository for most
- of the FAQ's you might think to look for and many you might not):
-
- IRC stands for "Internet Relay Chat". It was originally
- written by Jarkko Oikarinen (jto@tolsun.oulu.fi) in 1988. Since
- starting in Finland, it has been used in over 60 countries spanning
- the globe. It was designed as a replacement for the "talk" program
- but has become much much more than that. IRC is a multi-user chat
- system, where people convene on "channels" (a virtual place, usually
- with a topic of conversation) to talk in groups, or privately. IRC is
- constantly evolving, so the way you expect things to work one week may
- not be the way they work the next. Read the MOTD (message of the day)
- every time you use IRC to keep up on any new happenings or server
- updates.
- --
- Bob Quinn rcq@ftp.com
- FTP Software, Inc. No. Andover, MA
-
-